SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 41498: Generic Critical Error or unresponsive SAS session following PROC CIMPORT of a SAS/AF® Frame catalog

DetailsAboutRate It

When using PROC CIMPORT to read in a SAS transport file containing a SAS/AF frame catalog, you might receive the following error in the SAS log:

   NOTE: Proc CIMPORT begins to create/update catalog WORK.MO_DISC_CAPA
   NOTE: Entry DATAIMPORT.FRAME has been imported.
   
   ERROR:  Write Access Violation In Task [ SASCIMPO )
   Exception occurred at (01335EDF)
   Task Traceback
   Address   Frame     (DBGHELP API Version 4.0 rev 5)
   01335EDF  048DEB78  sashost:Main+0xCF24F
   012EF307  048DEB90  sashost:Main+0x88677
   66AC74A0  048DEBCC  sasccafe:mcn_main+0x164A0
   66AC6EE1  048DED30  sasccafe:mcn_main+0x15EE1
   66AC1E86  048DFE8C  sasccafe:mcn_main+0x10E86
   66881254  048DFF88  sascim:mcn_main+0x254
   01272B72  048DFFA0  sashost:Main+0xBEE2
   01276C90  048DFFB4  sashost:Main+0x10000
   7C80B713  048DFFEC  kernel32:GetModuleFileNameA+0x1B4

   ERROR: Generic critical error.
   ERROR: Error converting FORECAST.FRAME.  Entry will be deleted.

Another symptom of this problem was found when importing the transport file into SAS 9.2 on a 64-bit machine. In this case, instead of the error, the SAS session stopped responding.

To circumvent this problem, follow the steps below:

  1. In the originating SAS session, rename the original SCL entry for the problem Frame. For example if your Frame is named MYFRAME.FRAME, rename the Frame to MYFRAME_BACK.FRAME.
  2. Edit your Frame entry for the SCL entry you renamed, and open the SCL source window and then close. This will create a new, empty SCL entry for that Frame.
  3. Exit the Frame, but do not compile.
  4. Use PROC CPORT to create the transport file of the catalog.
  5. On the destination operating system, use PROC CIMPORT to read in the catalog from the transport file in step 4.
  6. In the destination SAS session, do the following to associate the backup SCL entry with the Frame:
    1. Delete the blank SCL entry created in step 2 that has the same name as the problem Frame.
    2. Rename the backup SCL entry back to its original name, like from MYFRAME_BACK.FRAME to MYFRAME.FRAME.
    3. Compile the Frame to once again associate the SCL code with its Frame.


Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS/AFz/OS9.1 TS1M09.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.1 TS1M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.1 TS1M09.3 TS1M0
Microsoft Windows 2000 Advanced Server9.1 TS1M0
Microsoft Windows 2000 Datacenter Server9.1 TS1M0
Microsoft Windows 2000 Server9.1 TS1M0
Microsoft Windows 2000 Professional9.1 TS1M0
Microsoft Windows NT Workstation9.1 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M09.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.1 TS1M09.3 TS1M0
Microsoft Windows XP Professional9.1 TS1M09.3 TS1M0
64-bit Enabled AIX9.1 TS1M09.3 TS1M0
64-bit Enabled HP-UX9.1 TS1M09.3 TS1M0
64-bit Enabled Solaris9.1 TS1M09.3 TS1M0
HP-UX IPF9.1 TS1M09.3 TS1M0
Linux9.1 TS1M09.3 TS1M0
OpenVMS Alpha9.1 TS1M09.3 TS1M0
Tru64 UNIX9.1 TS1M09.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.